LAN-EMULATION-CLIENT-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,enterprises,Counter32,Integer32FROM SNMPv2-SMI
TEXTUAL-CONVENTION,MacAddress,RowStatus,TruthValue,DisplayStringFROM SNMPv2-TC
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF
InterfaceIndexFROM IF-MIB
ifIndex FROM RFC1213-MIB
OwnerStringFROM RFC1271-MIB;leClientMIB MODULE-IDENTITYLAST-UPDATED"9802230000Z"ORGANIZATION"ATM Forum LAN Emulation Sub-Working Group"CONTACT-INFO"
The ATM Forum
2570 West El Camino Real, Suite 304
Mountain View, CA 94040-1313
Tel: +1-650-949-6700
Fax: +1-650-949-6705
E-mail: info@atmforum.com
Web: http://www.atmforum.com/
"DESCRIPTION"This module defines a portion of the management
information base (MIB) for managing ATM LAN Emulation
Client nodes. It is meant to be used in connection with
the AToM MIB and MIB-II / RFC 1573 'ifTable' entries
for each LEC / emulated 802.x network interface."REVISION"9505100000Z"DESCRIPTION"The LAST-UPDATED date of the MIB in the Version 1.0 LAN
Emulation Client management specification."REVISION"9802230000Z"DESCRIPTION"This MIB module now provides extensive support for LAN
Emulation Version 2.0 clients, and the optional ability
to query a proxy client (say, one attached to a bridge)
to find out how it would respond to a LE_ARP request."::={ atmfLanEmulation 1}-- --------------------------------------------------------------
---- If your compiler gives you trouble with the forward reference-- to 'atmfLanEmulation', you may need to move the definition to-- a non-standard place before the MODULE-IDENTITY statement.---- --------------------------------------------------------------atmForum OBJECTIDENTIFIER::={ enterprises 353}atmForumNetworkManagement OBJECTIDENTIFIER::={ atmForum 5}-- The object identifier subtree for ATM Forum LAN Emulation MIBsatmfLanEmulation OBJECTIDENTIFIER::={ atmForumNetworkManagement 3}leClientMIBObjects OBJECTIDENTIFIER::={ leClientMIB 1}-- This MIB module consists of the following groups:---- (1) LAN Emulation Client groups-- (a) Configuration group-- (b) Status group-- (c) Statistics group-- (d) Server VCC group---- (2) ifIndex mapping group---- (3) LEC ATM Addresses group---- (4) Registered LAN Destination groups-- (a) MAC addresses group-- (b) Route Descriptors group---- (5) LE_ARP cache groups-- (a) MAC address cache group-- (b) Route descriptor cache group---- (6) Multicast Forward VCC group---- (7) Proxy LE_ARP response groups-- (a) MAC address query group-- (b) Route descriptor query group---- (8) TLV table group---- Security management objects have been explicitly omitted from-- this MIB as being outside the scope of the V2.0 LAN Emulation-- specification.AtmLaneAddress::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"A twenty-octet binary string, containing a standard
ATM Forum address -- or the zero-length string,
indicating the absence of an address.
For LAN Emulation purposes, the eight-octet address
format is not used."SYNTAXOCTETSTRING(SIZE(0 | 20))VpiInteger::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"An integer large enough to hold a VPI. Objects that
use this textual convention should contain either
- A value which conforms to the AtmVpIdentifier
convention in the proposed ATM-TC-MIB, or
- Zero (if there is no circuit/path data).
AtmVpIdentifier is currently defined as
The VPI value for a VPL or VCL. The value VPI=0
is only allowed for a VCL. For ATM UNIs supporting
VPCs the VPI value ranges from 1 to 255. For ATM
UNIs supporting VCCs the VPI value ranges from 0
to 255. For ATM NNIs the VPI value ranges from 0
to 4095. The maximum VPI value cannot exceed the
value allowable by atmInterfaceMaxVpiBits defined
in ATM-MIB.
To align the textual conventions, VpiInteger now ranges
between 0 and 4095, instead of between 0 and 255."SYNTAXINTEGER(0..4095)VciInteger::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"An integer large enough to hold a VCI. Objects that
use this textual convention should contain either
- A value which conforms to the AtmVcIdentifier
convention in the proposed ATM-TC-MIB, or
- Zero (if there is no circuit data).
AtmVcIdentifier is currently defined as
The VCI value for a VCL. The maximum VCI value
cannot exceed the value allowable by
atmInterfaceMaxVciBits defined in ATM-MIB."SYNTAXINTEGER(0..65535)LeConnectionInterface::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"A combination flag and ifTable index, indicating
whether a LAN Emulation circuit exists - and, if
so, which interface is associated with it at the
point where it connects to a LE Client.
Objects of this type are always defined as part of
a set that includes
fooInterface LeConnectionInterface
fooVpi VpiInteger
fooVci VciInteger
The interpretation of these objects is as follows.
1. If no connection exists, 'fooInterface' has a
value of 0. Because Interfaces table entries
always have 'ifIndex' values larger than 0,
'fooInterface' reliably serves as a 'connection
exists' flag.
In this case, 'fooVpi' and 'fooVci' are
meaningless, and have the value 0.
2. If a PVC or SVC exists, 'fooInterface' is defined
to have the value of the MIB-II/RFC 1573 'ifIndex'
of the 'atm' interface associated with the VCC.
'fooVpi' and 'fooVci' will contain its VPI/VCI.
Therefore, ('fooInterface', 'fooVpi', 'fooVci')
give you an index into the AToM MIB which allows
you to examine and play with the circuit further.
3. If a proprietary connection (such as an internal
data path between co-located components) exists,
this specification does not mandate how it should
be managed. One option is to set 'fooInterface'
to the value of the MIB-II/RFC 1573 'ifIndex' for
the LAN Emulation Client. This indicates that a
connection exists, but is not being managed in the
same fashion as an ATM VCC."SYNTAXINTEGER(0..2147483647)LecState::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"An official protocol state of a LAN Emulation Client."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.3.1"SYNTAXINTEGER{initialState(1),lecsConnect(2),configure(3),join(4),initialRegistration(5),busConnect(6),operational(7)}LecDataFrameFormat::=TEXTUAL-CONVENTION
STATUScurrentDESCRIPTION"A 'LAN Type' value.
C2 LAN Type. The type of LAN that the LE Client is,
or wishes to become, a member of. This MUST be one
of Ethernet/IEEE 802.3, IEEE 802.5, or Unspecified."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"SYNTAXINTEGER{unspecified(1),aflane8023(2),aflane8025(3)}LecDataFrameSize::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"A 'Maximum Data Frame Size' value.
C3 Maximum Data Frame Size. The maximum AAL-5 SDU size
of a data frame that the LE Client wishes to send on
any Multicast Send VCC, or to receive on any
Multicast Send VCC or Multicast Forward VCC.
This parameter also specifies the maximum AAL-5 SDU
on all of a LE Client's non-multiplexed Data Direct
VCCs, and the maximum AAL-5 SDU - 12 (for overhead)
on all of a LE Client's LLC-multiplexed Data Direct
VCCs.
This setting MUST be either 1516, 1580, 4544, 9234,
or 18190 octets, or Unspecified. The 1580 value is
only available to 'V2 Capable' clients."REFERENCE"ATM Forum LAN Emulation V1 and V2 LUNI specifications,
Section 5.1.1"SYNTAXINTEGER{-- LANE 1.0unspecified(1),max1516(2),max4544(3),max9234(4),max18190(5),-- LANE 2.0max1580(6)}LeArpTableEntryType::=TEXTUAL-CONVENTIONSTATUScurrent
DESCRIPTION"Indicates how a LE_ARP table entry was created and
whether it is subject to aging.
other(1)
The LE_ARP entry does not fall into one of
the categories defined below.
learnedViaControl(2)
This LE_ARP entry was learned by using the
LE_ARP_REQUEST / LE_ARP_RESPONSE protocol,
or by otherwise observing relevant traffic
on Control VCCs.
Entries of this type are aged.
learnedViaData(3)
This LE_ARP entry was learned by observing
incoming traffic on Data VCCs.
Entries of this type are aged.
staticVolatile(4)
This LE_ARP entry was created by management.
It will not be aged. On the other hand, it
will not survive a restart of the client.
If an agent permits LE_ARP entries of this
type to be created, it may require that the
LAN Emulation Client be in the 'operational'
state at the time.
staticNonVolatile(5)
This LE_ARP entry was created by management.
It will not be aged, and it will survive a
restart of the client.
The values 'learnedViaData' and 'learnedViaControl'
can be read, but may not be written."SYNTAXINTEGER{other(1),learnedViaControl(2),learnedViaData(3),staticVolatile(4),staticNonVolatile(5)}-- ------------------------------------------------------------------- LAN Emulation Client configuration group--lecConfigTable OBJECT-TYPESYNTAXSEQUENCEOF LecConfigEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table describing all of the LAN Emulation Clients
implemented by this host. Each LE Client has a row
in the MIB-II/RFC 1573 Interfaces table (describing
the emulated packet interface it presents to higher
layers). Each LE Client also has a row in this and
other LEC MIB tables (describing its interface with
other LAN Emulation components).
This table contains configuration variables. Three
extension tables contain client status, performance
statistics, and information about control/multicast
VCCs.
Unlike hardware ports, LE Clients can be created by
management. However, the RFC 1573 Interfaces table
does not directly support row creation. Therefore,
creating or deleting a row in the lecConfigTable is
defined to have the side effect of creating or
deleting corresponding rows in
- the MIB-II / RFC 1573 Interfaces table,
- the 'lecMappingTable',
- the 'lecStatusTable',
- the 'lecServerVccTable',
- the 'lecStatisticsTable', and
- any other dependent tables
New Interfaces table rows for LAN Emulation Clients
always have 'ifAdminStatus' set to 'down'.
A Note On Indexing:
-------------------
Most of the tables in this MIB are indexed in whole
or in part by 'lecIndex' - not by 'ifIndex'.
Why is there a separate index?
Traditionally, ifIndex values are chosen by agents,
and are permitted to change across restarts. Using
ifIndex to index lecConfigTable could complicate
row creation and/or cause interoperability problems
(if each agent had special restrictions on ifIndex).
Having a separate index avoids these problems. "::={ leClientMIBObjects 1}lecConfigEntry OBJECT-TYPESYNTAX LecConfigEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each table entry contains configuration information
for one LAN Emulation Client.
Most of the objects are derived from Initial State
Parameters in the LAN Emulation specification."INDEX{ lecIndex }::={ lecConfigTable 1}
LecConfigEntry ::=SEQUENCE{---- Row indices, creation, and deletion.--
lecIndex INTEGER,
lecRowStatus RowStatus,
lecOwner OwnerString,---- Key parameters for Configure / Join phase. Note that-- these are not operational values - see lecStatusTable
-- for those.--
lecConfigMode INTEGER,
lecConfigLanType LecDataFrameFormat,
lecConfigMaxDataFrameSize LecDataFrameSize,
lecConfigLanName DisplayString,
lecConfigLesAtmAddress AtmLaneAddress,---- Other parameters. These may be changed either by the-- network manager or by the LE Configuration Server.--
lecControlTimeout INTEGER,
lecMaxUnknownFrameCount INTEGER,
lecMaxUnknownFrameTime INTEGER,
lecVccTimeoutPeriod Integer32,
lecMaxRetryCount INTEGER,
lecAgingTime INTEGER,
lecForwardDelayTime INTEGER,
lecExpectedArpResponseTime INTEGER,
lecFlushTimeOut INTEGER,
lecPathSwitchingDelay INTEGER,
lecLocalSegmentID INTEGER,
lecMulticastSendType INTEGER,
lecMulticastSendAvgRate Integer32,
lecMulticastSendPeakRate Integer32,
lecConnectionCompleteTimer INTEGER,---- New parameter for LANE 1.0 addendum--
lecConfigLecsAtmAddress AtmLaneAddress,---- Objects to support LANE 2.0--
lecInitialControlTimeout INTEGER,
lecControlTimeoutMultiplier INTEGER,
lecV2MaxUnknownFrameCount INTEGER,
lecConfigLocalSegmentID INTEGER,
lecConfigV2Capable TruthValue,
lecConfigSelectiveMulticast TruthValue,
lecForwardDisconnectTimeout INTEGER,
lecConfigLLCMultiplexCapable TruthValue,
lecMinReconfigureDelay INTEGER,
lecMaxReconfigureDelay INTEGER,
lecMaxBusConnectRetries INTEGER,
lecTokenRingExplorerExclude TruthValue}lecIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A value which uniquely identifies this conceptual
row in the lecConfigTable.
If the conceptual row identified by this value of
lecIndex is recreated following an agent restart,
the same value of lecIndex must be used to identify
the recreated row. (However, the Interfaces table
index associated with the client may change.)"::={ lecConfigEntry 1}lecRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object lets network managers create and delete
LAN Emulation Clients, on systems that support this
optional capability.
It does not control Joins and Terminations; they are
controlled by 'ifAdminStatus'. However, taking rows
out of service will have the side effect of changing
their 'ifAdminStatus' values to 'down', thus causing
any active emulated LAN connections to be terminated.
Within each conceptual lecConfigTable row, objects
which are writable may be modified regardless of the
value of lecRowStatus. It is not necessary to set a
row's status to 'notInService' first.
When creating a LAN Emulation Client, it is up to the
management station to determine a suitable 'lecIndex'.
To facilitate interoperability, agents should not put
any restrictions on the 'lecIndex' beyond the obvious
ones that it be valid and unused.
If you create a LAN Emulation Client via this object,
it will initially have
'ifAdminStatus' = 'down'
'ifOperStatus' = 'down'
'lecInterfaceState' = 'initialState' "::={ lecConfigEntry 2}lecOwner OBJECT-TYPESYNTAXOwnerString(SIZE(0..127))
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The entity that configured this entry and is therefore
using the resources assigned to it."::={ lecConfigEntry 3}lecConfigMode OBJECT-TYPESYNTAXINTEGER{automatic(1),manual(2)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates whether this LAN Emulation Client should
auto-configure the next time it is (re)started.
In automatic(1) mode, a client uses a LAN Emulation
Configuration Server to learn the ATM address of its
LAN Emulation Server, and to obtain other parameters.
lecConfig{ LanType, MaxDataFrameSize, LanName } are
used in the Configure request. lecConfigLesAtmAddress
is ignored.
In manual(2) mode, management tells the client the
ATM address of its LAN Emulation Server and the
values of other parameters.
lecConfig{ LanType, MaxDataFrameSize, LanName } are
used in the Join request. lecConfigLesAtmAddress
tells the client which LES to call."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Sections 3.4.1.1 and 5.3"DEFVAL{ automatic }::={ lecConfigEntry 4}lecConfigLanType OBJECT-TYPESYNTAXLecDataFrameFormatMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C2c LAN Type (configured).
The data frame format which this client will use the
next time it returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLanType will be."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{ unspecified }::={ lecConfigEntry 5}lecConfigMaxDataFrameSize OBJECT-TYPESYNTAXLecDataFrameSizeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C3c Maximum Data Frame Size (configured).
The maximum data frame size which this client will
use the next time it returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualMaxDataFrameSize will be."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{ unspecified }::={ lecConfigEntry 6}lecConfigLanName OBJECT-TYPESYNTAXDisplayString(SIZE(0..32))MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C5c ELAN Name (configured).
The ELAN Name this client will use the next time it
returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLanName will be."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecConfigEntry 7}lecConfigLesAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C9 LE Server ATM Address.
The LAN Emulation Server which this client will use
the next time it is started in manual configuration
mode.
When lecConfigMode is 'automatic', there is no need
to set this address, and no advantage to doing so.
The client will use the LECS to find a LES, putting
the auto-configured address in lecActualLesAtmAddress
while leaving lecConfigLesAtmAddress alone."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecConfigEntry 8}lecControlTimeout OBJECT-TYPE--
-- For LANE V1.0, this object had a default of 120.
--SYNTAXINTEGER(10..300)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C7 Control Time-out. Time out period used for
timing out most request/response control frame
interactions, as specified elsewhere [in the
LAN Emulation specification].
In LANE V2.0, this value specifies the maximum
cumulative timeout for an exponential backoff
algorithm.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{30}::={ lecConfigEntry 9}lecMaxUnknownFrameCount OBJECT-TYPESYNTAXINTEGER(1..10)UNITS"frames"MAX-ACCESSread-createSTATUSdeprecatedDESCRIPTION"This is the LANE V1.0 version of 'C10 Maximum Unknown
Frame Count'. It should not be implemented except as
required for backwards compatibility.
It has been deprecated because LANE V2.0 permits this
parameter to take values up to 20 -- a revision which
doesn't seem to be allowed under rules in RFC 1902."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 10}
lecMaxUnknownFrameTime OBJECT-TYPESYNTAXINTEGER(1..60)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C11 Maximum Unknown Frame Time. Within the period of
time defined by the Maximum Unknown Frame Time, a
LE Client will send no more than Maximum Unknown
Frame Count frames to the BUS for a given unicast
LAN Destination, and it must also initiate the
address resolution protocol to resolve that LAN
Destination.
LANE V2.0 changes this to 'will send no more than
Maximum Unknown Frame Count frames to the BUS ...
without initiating the [LE_ARP]', implying that a
LANE V2.0 client is not always required to send a
LE_ARP_REQUEST along with the unknown frames.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 11}lecVccTimeoutPeriod OBJECT-TYPESYNTAXInteger32UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C12 VCC Time-out Period. A LE Client SHOULD release
any Data Direct VCC that it has not used to
transmit or receive any data frames for the
length of the VCC Time-out Period. This parameter
is only meaningful for SVC Data Direct VCCs
signalled with the Ethernet/IEEE 802.3 LE Data
Direct VCC B-LLI value or the IEEE 802.5 LE Data
Direct VCC B-LLI value. It should not be used for
any SVC signalled with the LLC-Multiplexed B-LLI
value.
This time value is expressed in seconds. The default
value is 20 minutes. A value of 0 seconds means that
the timeout period is infinite. Negative values will
be rejected by the agent."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{1200}::={ lecConfigEntry 12}
lecMaxRetryCount OBJECT-TYPESYNTAXINTEGER(0..2)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C13 Maximum Retry Count. A LE CLient MUST not retry
a LE_ARP_REQUEST for a given frame's LAN
destination more than Maximum Retry Count times,
after the first LE_ARP_REQUEST for that same
frame's LAN destination."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 13}lecAgingTime OBJECT-TYPESYNTAXINTEGER(10..300)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C17 Aging Time. The maximum time that a LE Client
will maintain an entry for a unicast LAN
Destination in its LE_ARP cache in the absence
of a verification of that relationship.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{300}::={ lecConfigEntry 14}lecForwardDelayTime OBJECT-TYPESYNTAXINTEGER(4..30)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C18 Forward Delay Time. The maximum time that a LE
Client will maintain an entry for a non-local MAC
address in its LE_ARP cache in the absence of a
verification of that relationship, as long as the
Topology Change flag C19 is true.
lecForwardDelayTime SHOULD BE less than lecAgingTime.
When it is not, lecAgingTime governs LE_ARP aging.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{15}::={ lecConfigEntry 15}lecExpectedArpResponseTime OBJECT-TYPESYNTAXINTEGER(1..30)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C20 Expected LE_ARP Reponse Time. The maximum time
that the LEC expects an LE_ARP_REQUEST/
LE_ARP_RESPONSE cycle to take. Used for retries
and verifies.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 16}lecFlushTimeOut OBJECT-TYPESYNTAXINTEGER(1..4)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C21 Flush Time-out. Time limit to wait to receive a
LE_FLUSH_RESPONSE after the LE_FLUSH_REQUEST has
been sent before taking recovery action.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{4}::={ lecConfigEntry 17}lecPathSwitchingDelay OBJECT-TYPESYNTAXINTEGER(1..8)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C22 Path Switching Delay. The time since sending a
frame to the BUS after which the LE Client may
assume that the frame has been either discarded
or delivered to the recipient. May be used to
bypass the Flush protocol.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{6}::={ lecConfigEntry 18}lecLocalSegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSread-createSTATUSdeprecatedDESCRIPTION"C23 Local Segment ID. The segment ID of the emulated
LAN. This is only required for IEEE 802.5 clients
that are Source Routing bridges.
This object has been deprecated and replaced by a pair
of Config/Actual objects. It shouldn't be implemented
except as required for backwards compatibility."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"::={ lecConfigEntry 19}lecMulticastSendType OBJECT-TYPESYNTAXINTEGER{bestEffort(1),variableBitRate(2),constantBitRate(3)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C24 Multicast Send VCC Type. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
This is the method to be used by the LE Client
when specifying traffic parameters when it sets
up the Multicast Send VCC for this emulated LAN."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecConfigEntry 20}lecMulticastSendAvgRate OBJECT-TYPE
SYNTAXInteger32UNITS"cells per second"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C25 Multicast Send VCC AvgRate. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
Forward and Backward Sustained Cell Rate to be
requested by LE Client when setting up Multicast
Send VCC, if using Variable bit rate codings."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecConfigEntry 21}lecMulticastSendPeakRate OBJECT-TYPESYNTAXInteger32UNITS"cells per second"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C26 Multicast Send VCC PeakRate. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
Forward and Backward Peak Cell Rate to be
requested by LE Client when setting up the
Multicast Send VCC when using either Variable or
Constant bit rate codings."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecConfigEntry 22}lecConnectionCompleteTimer OBJECT-TYPESYNTAXINTEGER(1..10)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C28 Connection Complete Timer. Optional. In
Connection Establishment this is the time period
in which data or a READY_IND message is expected
from a Calling Party.
This time value is expressed in seconds."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"DEFVAL{4}::={ lecConfigEntry 23}
lecConfigLecsAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"LE Configuration Server ATM address.
A manually-configured LECS address that this client
may use in its attempts at auto-configuration."REFERENCE"LANE 1.0 addendum"::={ lecConfigEntry 24}lecInitialControlTimeout OBJECT-TYPESYNTAXINTEGER(1..10)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C7i Initial Control Time-out.
In LANE V2.0, control time-out consists of an initial
time-out of C7i seconds, a retry multiplier (or
logarithmic back-off base) of C7x, and a cumulative
maximum time-out of C7 seconds."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{5}::={ lecConfigEntry 25}lecControlTimeoutMultiplier OBJECT-TYPESYNTAXINTEGER(2..5)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C7x Control Time-out Multiplier.
In LANE V2.0, control time-out consists of an initial
time-out of C7i seconds, a retry multiplier (or
logarithmic back-off base) of C7x, and a cumulative
maximum time-out of C7 seconds."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{2}::={ lecConfigEntry 26}lecV2MaxUnknownFrameCount OBJECT-TYPESYNTAXINTEGER(1..20)
UNITS"frames"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C10 Maximum Unknown Frame Count. See the description
of lecMaxUnknownFrameTime above.
This object may be used with both LANE V1.0 clients &
LANE V2.0 clients. For LANE V1.0 clients, this value
should be in the range 1..10, with a default of 1."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{10}::={ lecConfigEntry 27}lecConfigLocalSegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C23c Local Segment ID (configured). The segment ID of
the emulated LAN. This is only required for IEEE
802.5 clients that are Source Routing bridges.
A setting which this client will use the next time it
returns to the Initial State.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLocalSegmentID will be."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecConfigEntry 28}lecConfigV2Capable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C29c V2 Capable (configured).
A setting which this client will use the next time it
returns to the Initial State.
Indicates whether this client is set up to behave as
a LANE V2 client.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualV2Capable will be."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecConfigEntry 29}lecConfigSelectiveMulticast OBJECT-TYPE
SYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C32c Selective Multicast (configured).
A setting which this client will use the next time it
returns to the Initial State.
Indicates if this client is configured to register to
receive specific multicast destination MAC addresses.
Must not be 'true' if lecConfigV2Capable is 'false'.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualSelectiveMulticast will be."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecConfigEntry 30}lecForwardDisconnectTimeout OBJECT-TYPESYNTAXINTEGER(10..300)UNITS"seconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C33 Forward Disconnect Time-out
If the LE Client detects that the BUS has had no
Multicast Forward VCCs to the LE Client for time
Forward Disconnect Time-out, the LE Client MUST
disconnect from the BUS and try to re-establish
a new connection."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{60}::={ lecConfigEntry 31}lecConfigLLCMultiplexCapable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C34c LLC Multiplex Capable (configured).
A setting which this client will use the next time it
returns to the Initial State.
Gives a network manager an optional method to disable
LLC multiplexing on a LANE V2 client that supports it.
Cannot be used to enable LLC multiplexing on products
that do not support it.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLLCMultiplexCapable will be."
REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecConfigEntry 32}lecMinReconfigureDelay OBJECT-TYPESYNTAXINTEGER(1..10000)UNITS"milliseconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C37 Minimum Reconfigure Delay.
The minimum time that a LE client must wait before
retrying reconfiguration. This setting must be
less than or equal to lecMaxReconfigureDelay."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 33}lecMaxReconfigureDelay OBJECT-TYPESYNTAXINTEGER(1..10000)UNITS"milliseconds"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C38 Maximum Reconfigure Delay.
The maximum time that a LE client must wait before
retrying reconfiguration. This setting must be
greater than or equal to lecMinReconfigureDelay."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{5000}::={ lecConfigEntry 34}lecMaxBusConnectRetries OBJECT-TYPESYNTAXINTEGER(0..2)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"C39 Maximum BUS Connect Retries.
The maximum number of times that a LE Client can try
to establish the Default Multicast Send VCC before
returning to the configuration procedure."REFERENCE
"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"DEFVAL{1}::={ lecConfigEntry 35}lecTokenRingExplorerExclude OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"C40 Token Ring Explorer Frame Exclude.
This indicates whether or not the LE Client wishes to
receive Token Ring explorer frames other than those
directed to one of its registered MAC addresses.
Normally, only bridges need to receive such explorer
frames. This parameter only applies to token-ring
ELANs. This parameter MUST NOT change without
restarting the Configure phase."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecConfigEntry 36}-- ------------------------------------------------------------------- LAN Emulation Client status group--lecStatusTable OBJECT-TYPESYNTAXSEQUENCEOF LecStatusEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A read-only table containing identification, status,
and operational information about the LAN Emulation
Clients this agent manages."::={ leClientMIBObjects 2}lecStatusEntry OBJECT-TYPESYNTAX LecStatusEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each table entry contains information about one LAN
Emulation Client."AUGMENTS{ lecConfigEntry }::={ lecStatusTable 1}
LecStatusEntry ::=SEQUENCE{---- Client identification--
lecIfIndex InterfaceIndex,
lecPrimaryAtmAddress AtmLaneAddress,
lecID INTEGER,---- Client status and protocol version--
lecInterfaceState LecState,
lecLastFailureRespCode INTEGER,
lecLastFailureState LecState,
lecProtocol INTEGER,
lecVersion INTEGER,
lecTopologyChange TruthValue,---- Operational parameters and their source--
lecConfigServerAtmAddress AtmLaneAddress,
lecConfigSource INTEGER,
lecActualLanType LecDataFrameFormat,
lecActualMaxDataFrameSize LecDataFrameSize,
lecActualLanName DisplayString,
lecActualLesAtmAddress AtmLaneAddress,
lecProxyClient TruthValue,---- LAN Emulation Version 2.0 additions--
lecActualLocalSegmentID INTEGER,
lecActualV2Capable TruthValue,
lecElanID Integer32,
lecActualSelectiveMulticast TruthValue,
lecActualLLCMultiplexCapable TruthValue,
lecPreferredLesAddress AtmLaneAddress,
lecStoresServiceCategories TruthValue}lecIfIndex OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object identifies the logical interface number
('ifIndex') assigned to this client, and is used to
identify corresponding rows in the Interfaces MIB.
Note that re-initialization of the management agent
may cause a client's 'lecIfIndex' to change."::={ lecStatusEntry 1}lecPrimaryAtmAddress OBJECT-TYPE
SYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C1 LE Client's ATM Addresses.
The primary ATM address of this LAN Emulation Client.
This address is used to establish the Control Direct
and Multicast Send VCCs, and may also be used to set
up Data Direct VCCs.
A client may have additional ATM addresses for use
with Data Direct VCCs. These addresses are readable
via the lecAtmAddressTable."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 2}lecID OBJECT-TYPESYNTAXINTEGER(0..65279)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C14 LE Client Identifier. Each LE Client requires a
LE Client Identifier (LECID) assigned by the LE
Server during the Join phase. The LECID is placed
in control requests by the LE Client and MAY be
used for echo suppression on multicast data frames
sent by that LE Client. This value MUST NOT
change without terminating the LE Client and
returning to the Initial state. A valid LECID
MUST be in the range X'0001' through X'FEFF'.
The value of this object is only meaningful for a LEC
that is connected to a LES. For a LEC which does not
belong to an emulated LAN, the value of this object
is defined to be 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 3}lecInterfaceState OBJECT-TYPESYNTAXLecStateMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The current state of the LAN Emulation Client.
Note that 'ifOperStatus' is defined to be 'up' when,
and only when, 'lecInterfaceState' is 'operational'."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.3.1"::={ lecStatusEntry 4}
lecLastFailureRespCode OBJECT-TYPESYNTAXINTEGER{none(1),timeout(2),undefinedError(3),versionNotSupported(4),invalidRequestParameters(5),duplicateLanDestination(6),duplicateAtmAddress(7),insufficientResources(8),accessDenied(9),invalidRequesterId(10),invalidLanDestination(11),invalidAtmAddress(12),noConfiguration(13),leConfigureError(14),insufficientInformation(15),---- LANE V2.0--tlvNotFound(16)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Status code from the last failed Configure response
or Join response. Failed responses are those for
which the LE_CONFIGURE_RESPONSE / LE_JOIN_RESPONSE
frame contains a non-zero code, or fails to arrive
within a timeout period.
If none of this client's requests have failed, this
object has the value 'none'.
If the failed response contained a STATUS code that
is not defined in the LAN Emulation specification,
this object has the value 'undefinedError'.
The value 'timeout' is self-explanatory.
Other failure codes correspond to those defined in
the specification, although they may have different
numeric values."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 4.2, Table 13"::={ lecStatusEntry 5}lecLastFailureState OBJECT-TYPESYNTAXLecStateMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The state this client was in when it updated the
'lecLastFailureRespCode'.
If 'lecLastFailureRespCode' is 'none', this object
has the value initialState(1)."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.3.1"::={ lecStatusEntry 6}lecProtocol OBJECT-TYPESYNTAXINTEGER(1..255)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The LAN Emulation protocol which this client supports,
and specifies in its LE_JOIN_REQUESTs."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 4.2"::={ lecStatusEntry 7}lecVersion OBJECT-TYPESYNTAXINTEGER(1..255)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The LAN Emulation protocol version which this client
supports, and specifies in its LE_JOIN_REQUESTs."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 4.2"::={ lecStatusEntry 8}lecTopologyChange OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C19 Topology Change. Boolean indication that the LE
Client is using the Forward Delay Time C18,
instead of the Aging Time C17, to age non-local
entries in its LE_ARP cache C16.
For a client which is not connected to the LES, this
object is defined to have the value 'false'."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 9}lecConfigServerAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The ATM address of the LAN Emulation Configuration
Server (if known) or the empty string (otherwise)."::={ lecStatusEntry 10}lecConfigSource OBJECT-TYPESYNTAXINTEGER{gotAddressViaIlmi(1),usedWellKnownAddress(2),usedLecsPvc(3),didNotUseLecs(4),usedConfiguredAddress(5),configInProgress(6)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates whether this LAN Emulation Client used the
LAN Emulation Configuration Server, and, if so, what
method it used to establish the Configuration Direct
VCC.
The value 'configInProgress' indicates configuration
is in progress, and may be used to troubleshoot LECs
that get stuck in the configuration phase."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.2; LANE 1.0 and LEC MIB 1.0 addendums"::={ lecStatusEntry 11}lecActualLanType OBJECT-TYPESYNTAXLecDataFrameFormatMAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"C2 LAN Type.
The data frame format that this LAN Emulation Client
is using right now. This may come from
* lecConfigLanType,
* the LAN Emulation Configuration Server, or
* the LAN Emulation Server
This value is related to 'ifMtu' and 'ifType'. See
the LEC management specification for more details."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 12}lecActualMaxDataFrameSize OBJECT-TYPESYNTAXLecDataFrameSizeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C3 Maximum Data Frame Size.
The maximum data frame size that this LAN Emulation
client is using right now. This may come from
* lecConfigMaxDataFrameSize,
* the LAN Emulation Configuration Server, or
* the LAN Emulation Server "REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 13}lecActualLanName OBJECT-TYPESYNTAXDisplayString(SIZE(0..32))MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C5 ELAN Name.
The identity of the emulated LAN which this client
last joined, or wishes to join. This may come from
* lecConfigLanName,
* the LAN Emulation Configuration Server, or
* the LAN Emulation Server "REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 14}lecActualLesAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C9 LE Server ATM Address.
The LAN Emulation Server address currently in use or
most recently attempted.
If no LAN Emulation Server attachment has been tried,
this object's value is the zero-length string."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 15}lecProxyClient OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C4 Proxy.
Indicates whether this client is acting as a proxy.
Proxy clients are allowed to represent unregistered
MAC addresses and route descriptors, and receive
copies of LE_ARP_REQUEST frames for such LAN
Destinations."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ lecStatusEntry 16}lecActualLocalSegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C23 Local Segment ID. The segment ID of the emulated
LAN. This is only required for IEEE 802.5 clients
that are Source Routing bridges."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 17}lecActualV2Capable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C29 V2 Capable.
If set, the LE Client must exhibit LANE v2 behavior
where it differs in its requirements from LANE v1
behavior. If clear, the LE Client must exhibit LANE
v1 behavior in those cases. This variable is set or
cleared according to the presence or absence of the
V2 Required FLAGS bit in the LE_JOIN_RESPONSE."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 18}lecElanID OBJECT-TYPE
SYNTAXInteger32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C31 ELAN-ID.
The ELAN-ID to be used in all LANE LLC-multiplexed
data frames sent or received by this client. This
object takes the value 0 if the LES is a LANE V1.0
LES. The initial value of this object is 0."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 19}lecActualSelectiveMulticast OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C32 Selective Multicast.
This indicates whether or not the LE Client will
register to receive specific multicast destination
MAC addresses. If this flag is set, the LE Client
MUST issue a LE_REGISTER_REQUEST for all of the
multicast or group MAC adddresses in C15, except
for the broadcast MAC address. If this variable is
clear, the LE Client MUST NOT issue a
LE_REGISTER_REQUEST for any multicast MAC address,
and can expect to receive all multicast frames from
the BUS."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 20}lecActualLLCMultiplexCapable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"C34 LLC Multiplex Capable.
If set, this variable indicates that the LE Client
can accept and process LLC-multiplexed Data Direct
VCCs. If clear, it indicates that the LE Client
will refuse to accept LLC-multiplexed Data Direct
VCCs. This variable MUST be clear if the LE Client
is connected to a LANE v1 LES."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 21}lecPreferredLesAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-only
STATUScurrentDESCRIPTION"C35 Preferred LES Address.
The ATM address of the preferred LE Server. This
variable is set during the Configuration phase by
copying the contents of the Preferred LES TLV
received in the LE_CONFIGURE_RESPONSE."REFERENCE"ATM Forum LAN Emulation V2.0 LUNI specification,
Section 5.1.1"::={ lecStatusEntry 22}lecStoresServiceCategories OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates whether or not the client saves Service
Category TLV data from LE_ARP_RESPONSEs and makes
it available through leArpTable and leRDArpTable."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ lecStatusEntry 23}-- ------------------------------------------------------------------- LAN Emulation Client - ifIndex Mapping Table--lecMappingTable OBJECT-TYPESYNTAXSEQUENCEOF LecMappingEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table mapping the 'ifIndex' values of 'aflane8023'
and 'aflane8025' interfaces to the 'lecIndex' values
of the corresponding LAN Emulation Clients."::={ leClientMIBObjects 3}lecMappingEntry OBJECT-TYPESYNTAX LecMappingEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each row describes one ifIndex --> lecIndex mapping."INDEX{ ifIndex }::={ lecMappingTable 1}
LecMappingEntry ::=SEQUENCE{
lecMappingIndex INTEGER}
lecMappingIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The 'lecIndex' of the client which implements the
specified interface."::={ lecMappingEntry 1}-- ------------------------------------------------------------------- LAN Emulation Client - Statistics table--lecStatisticsTable OBJECT-TYPESYNTAXSEQUENCEOF LecStatisticsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An extension table containing traffic statistics for
all the LAN Emulation Clients this host implements."::={ leClientMIBObjects 4}lecStatisticsEntry OBJECT-TYPESYNTAX LecStatisticsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each row in this table contains traffic statistics
for one LAN Emulation client."AUGMENTS{ lecConfigEntry }::={ lecStatisticsTable 1}
LecStatisticsEntry ::=SEQUENCE{
lecArpRequestsOut Counter32,
lecArpRequestsIn Counter32,
lecArpRepliesOut Counter32,
lecArpRepliesIn Counter32,
lecControlFramesOut Counter32,
lecControlFramesIn Counter32,
lecSvcFailures Counter32,---- LEC MIB Version 2.0 additions--
lecFlowFailures Counter32,
lecEchoDiscards Counter32,
lecFilteredMulticasts Counter32
}lecArpRequestsOut OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of LE_ARP_REQUESTs sent over the LUNI by
this LAN Emulation Client."::={ lecStatisticsEntry 1}lecArpRequestsIn OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of LE_ARP_REQUESTs received over the LUNI
by this LAN Emulation Client.
Requests may arrive on the Control Direct VCC or on
the Control Distribute VCC, depending upon how the
LES is implemented and the chances it has had for
learning. This counter covers both VCCs."::={ lecStatisticsEntry 2}lecArpRepliesOut OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of LE_ARP_RESPONSEs sent over the LUNI by
this LAN Emulation Client."::={ lecStatisticsEntry 3}lecArpRepliesIn OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of LE_ARP_RESPONSEs received over the LUNI
by this LAN Emulation Client. This count includes
all such replies, whether solicited or not.
Replies may arrive on the Control Direct VCC or on
the Control Distribute VCC, depending upon how the
LES is implemented. This counter covers both VCCs."::={ lecStatisticsEntry 4}lecControlFramesOut OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of control packets sent by this
LAN Emulation Client over the LUNI."::={ lecStatisticsEntry 5}
lecControlFramesIn OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of control packets received by this
LAN Emulation Client over the LUNI."::={ lecStatisticsEntry 6}lecSvcFailures OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of
* outgoing LAN Emulation SVCs which this client
tried, but failed, to open;
* incoming LAN Emulation SVCs which this client
tried, but failed to establish; and
* incoming LAN Emulation SVCs which this client
rejected for protocol or security reasons.
It does not include SVC failures for LLC-multiplexed
connections."::={ lecStatisticsEntry 7}lecFlowFailures OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of
* outgoing LLC-multiplexed LAN Emulation flows
which this client tried, but failed, to open;
* incoming LLC-multiplexed LAN Emulation flows
which this client did not accept / establish.
Only failures of which the LEC is aware and which are
clearly LANE-related need to be counted."::={ lecStatisticsEntry 8}lecEchoDiscards OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of incoming data frames which were thrown
away because they were echo frames (e. g., copies of
this client's own outgoing traffic).
Such discards are a normal part of LAN Emulation and
not a cause for alarm. So this counter is mainly of
interest for helping to estimate average frame size.
Frames that are included in this count should not be
included in ifInDiscards, so as to avoid setting off
false alarms."::={ lecStatisticsEntry 9}lecFilteredMulticasts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of incoming data frames which were thrown
away by the client because they were for a multicast
(or group) address upper-layer software didn't want.
If this counter indicates that a LEC is being loaded
down with an excessive number of unwanted multicasts,
one possible solution is to install LECs and LES/BUS
pairs with better support for selective multicasting.
Frames that are included in this count should not be
included in ifInDiscards, so as to avoid setting off
false alarms."::={ lecStatisticsEntry 10}-- ------------------------------------------------------------------- LAN Emulation Client - Server VCC table--lecServerVccTable OBJECT-TYPESYNTAXSEQUENCEOF LecServerVccEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table identifying the Control VCCs and Multicast
VCCs for each LAN Emulation Client which this host
implements.
For LANE 2.0 clients, the table identifies Control
VCCs and Default Multicast Send VCCs."::={ leClientMIBObjects 5}lecServerVccEntry OBJECT-TYPESYNTAX LecServerVccEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each row in this table describes the Control VCCs
and Multicast VCCs for one LEC."AUGMENTS{ lecConfigEntry }::={ lecServerVccTable 1}
LecServerVccEntry ::=SEQUENCE{---- Note that the 'lec*Interface' objects double as 'connection-- exists' flags.--
lecConfigDirectInterface LeConnectionInterface,
lecConfigDirectVpi VpiInteger,
lecConfigDirectVci VciInteger,
lecControlDirectInterface LeConnectionInterface,
lecControlDirectVpi VpiInteger,
lecControlDirectVci VciInteger,
lecControlDistributeInterface LeConnectionInterface,
lecControlDistributeVpi VpiInteger,
lecControlDistributeVci VciInteger,
lecMulticastSendInterface LeConnectionInterface,
lecMulticastSendVpi VpiInteger,
lecMulticastSendVci VciInteger,---- The Multicast Forward variables are not meaningful for LANE-- V2.0 clients operating in V2.0 mode.--
lecMulticastForwardInterface LeConnectionInterface,
lecMulticastForwardVpi VpiInteger,
lecMulticastForwardVci VciInteger}lecConfigDirectInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The interface associated with the Configuration
Direct VCC. If no Configuration Direct VCC exists,
this object has the value 0. Otherwise, the objects
( lecConfigDirectInterface,
lecConfigDirectVpi, lecConfigDirectVci )
identify the circuit."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.1"::={ lecServerVccEntry 1}lecConfigDirectVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Configuration Direct VCC exists, this object
contains the VPI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.1"::={ lecServerVccEntry 2}
lecConfigDirectVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Configuration Direct VCC exists, this object
contains the VCI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.1"::={ lecServerVccEntry 3}lecControlDirectInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The interface associated with the Control Direct VCC.
If no Control Direct VCC exists, this object has the
value 0. Otherwise, the objects
( lecControlDirectInterface,
lecControlDirectVpi, lecControlDirectVci )
identify the circuit."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.2"::={ lecServerVccEntry 4}lecControlDirectVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Control Direct VCC exists, this object
contains the VPI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.2"::={ lecServerVccEntry 5}lecControlDirectVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Control Direct VCC exists, this object
contains the VCI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."
REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.2"::={ lecServerVccEntry 6}lecControlDistributeInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The interface associated with the Control Distribute
VCC. If no Control Distribute VCC has been set up to
this client, this object has the value 0. Otherwise,
the objects
( lecControlDistributeInterface,
lecControlDistributeVpi,
lecControlDistributeVci )
identify the circuit."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.3"::={ lecServerVccEntry 7}lecControlDistributeVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Control Distribute VCC exists, this object
contains the VPI which identifies that VCC at the
point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.3"::={ lecServerVccEntry 8}lecControlDistributeVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Control Distribute VCC exists, this object
contains the VCI which identifies that VCC at the
point where it connects to this LE client.
Otherwise, this object contains the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.1.3"::={ lecServerVccEntry 9}lecMulticastSendInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSread-only
STATUScurrentDESCRIPTION"The interface associated with the Multicast Send
VCC. If no Multicast Send VCC exists, this object
has the value 0. Otherwise, the objects
( lecMulticastSendInterface,
lecMulticastSendVpi, lecMulticastSendVci )
identify the circuit."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.2"::={ lecServerVccEntry 10}lecMulticastSendVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Multicast Send VCC exists, this object
contains the VPI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.2"::={ lecServerVccEntry 11}lecMulticastSendVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the Multicast Send VCC exists, this object
contains the VCI which identifies that VCC at
the point where it connects to this LE client.
Otherwise, this object has the value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.2"::={ lecServerVccEntry 12}lecMulticastForwardInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"For a LANE V1.0 client:
-----------------------
The interface associated with the Multicast Forward
VCC. If no Multicast Forward VCC has been set up to
this client, this object has the value 0. Otherwise,
the objects
( lecMulticastForwardInterface,
lecMulticastForwardVpi,
lecMulticastForwardVci )
identify the circuit.
For a LANE V2.0 client in LANE 2.0 mode:
----------------------------------------
The value 0. There may not be a single VCC that can
be identified as the 'default'."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.3"::={ lecServerVccEntry 13}lecMulticastForwardVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"For a LANE V1.0 client:
-----------------------
If the Multicast Forward VCC exists, this object
contains the VPI which identifies that VCC at the
point where it connects to this LE client.
Otherwise, this object has the value 0.
For a LANE V2.0 client in LANE 2.0 mode:
----------------------------------------
The value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.3"::={ lecServerVccEntry 14}lecMulticastForwardVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"For a LANE V1.0 client:
-----------------------
If the Multicast Forward VCC exists, this object
contains the VCI which identifies that VCC at the
point where it connects to this LE client.
Otherwise, this object has the value 0.
For a LANE V2.0 client in LANE 2.0 mode:
----------------------------------------
The value 0."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.2.2.2.3"::={ lecServerVccEntry 15}-- ------------------------------------------------------------------- LAN Emulation Client - ATM Addresses table--lecAtmAddressTable OBJECT-TYPESYNTAXSEQUENCEOF LecAtmAddressEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table listing all of the ATM addresses belonging
to this host's LAN Emulation Clients."::={ leClientMIBObjects 6}lecAtmAddressEntry OBJECT-TYPESYNTAX LecAtmAddressEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each row in this table describes one of a client's
ATM addresses."INDEX{ lecIndex, lecAtmAddress }::={ lecAtmAddressTable 1}
LecAtmAddressEntry ::=SEQUENCE{
lecAtmAddress AtmLaneAddress,
lecAtmAddressStatus RowStatus,---- New for LANE 2.0--
lecAtmAddressMuxed INTEGER}lecAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The ATM address this row describes. This could be
either a primary address or a secondary address."::={ lecAtmAddressEntry 1}lecAtmAddressStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Used to create and delete rows in this table.
A management station may not change the status of a
primary ATM address to 'notInService' or 'destroy'
unless the client's ifAdminStatus is 'down', and the
client's lecInterfaceState is 'initialState'.
Secondary ATM addresses may be destroyed at any time
permitted by the agent."::={ lecAtmAddressEntry 2}lecAtmAddressMuxed OBJECT-TYPESYNTAXINTEGER{muxed(1),notMuxed(2),both(3),
none(4)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates what type(s) of connections the LEC is
willing to establish at this ATM address."::={ lecAtmAddressEntry 3}-- ------------------------------------------------------------------- LAN Emulation Client Registered MAC Addresses group--lecMacAddressTable OBJECT-TYPESYNTAXSEQUENCEOF LecMacAddressEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains entries for all of the registered
MAC addresses belonging to this agent's LE clients.
For all LANE clients, this includes
C6 Local Unicast MAC Address(es). Each LE Client has
zero or more local unicast MAC addresses. In an
operational LE Client, every address in this
variable MUST have been registered with the LE
Server. Two LE CLients joined to the same
emulated LAN MUST NOT have the same local unicast
MAC address. A LE Client's MAC addresses may
change during normal operations. When answering
a LE_ARP_REQUEST for any address in this list, the
'Remote Address' bit in the FLAGS field of the
LE_ARP_RESPONSE MUST be clear.
For a LANE V2.0 client, this also includes <registered>
multicast MAC addresses in C15."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ leClientMIBObjects 7}lecMacAddressEntry OBJECT-TYPESYNTAX LecMacAddressEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each table row describes a (MAC address, ATM address)
pair registered for a particular client."INDEX{ lecIndex, lecMacAddress }::={ lecMacAddressTable 1}
LecMacAddressEntry ::=
SEQUENCE{
lecMacAddress MacAddress,
lecMacAddressAtmBinding AtmLaneAddress,---- New for LANE 2.0--
lecMacAddressMuxedAtmBinding AtmLaneAddress,
lecMacAddressServiceCategory INTEGER}lecMacAddress OBJECT-TYPESYNTAXMacAddressMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A unicast or multicast MAC address that this LEC has
registered with its LES.
Note that the LANE V1.0 specification does not allow
V1.0 clients to register multicast addresses."::={ lecMacAddressEntry 1}lecMacAddressAtmBinding OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The non-multiplexed ATM address, if any, registered
for 'lecMacAddress'."::={ lecMacAddressEntry 2}lecMacAddressMuxedAtmBinding OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The LLC-multiplexed ATM address, if any, registered
for 'lecMacAddress'."::={ lecMacAddressEntry 3}lecMacAddressServiceCategory OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A bitmap describing the service categories which the
LEC supports for this MAC address.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"
::={ lecMacAddressEntry 4}-- ------------------------------------------------------------------- LAN Emulation Client Registered Route Descriptors group--lecRouteDescrTable OBJECT-TYPESYNTAXSEQUENCEOF LecRouteDescrEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table lists all of the Local Route Descriptors
which are registered by this host's LAN Emulation
Clients.
C8 Local Route Descriptor(s). Local Route
Descriptors exist only for source-routed IEEE
802.5 LE Clients that are Source-Route Bridges.
All Local Route Descriptors in any given emulated
LAN MUST be unique. A LE Client MAY have zero or
more Local Route Descriptors and these Local Route
Descriptors MAY change during normal operation.
In an operational LE Client, every Local Route
Descriptor in C8 MUST have been registered with
the LE Server. When answering a LE_ARP_REQUEST
for any address in this list, the 'Remote Address'
bit in the FLAGS field of the LE_ARP_RESPONSE MUST
be clear."REFERENCE"ATM Forum LAN Emulation Over ATM Specification, V1.0
and V2.0, Section 5.1.1"::={ leClientMIBObjects 8}lecRouteDescrEntry OBJECT-TYPESYNTAX LecRouteDescrEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each table row describes a (Route Descriptor, ATM
address) pair registered for a particular client."INDEX{ lecIndex, lecRouteDescrSegmentID,
lecRouteDescrBridgeNumber }::={ lecRouteDescrTable 1}
LecRouteDescrEntry ::=SEQUENCE{
lecRouteDescrSegmentID INTEGER,
lecRouteDescrBridgeNumber INTEGER,
lecRouteDescrAtmBinding AtmLaneAddress,---- New for LANE 2.0--
lecRouteDescrMuxedAtmBinding AtmLaneAddress,
lecRouteDescrServiceCategory INTEGER}lecRouteDescrSegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The LAN ID portion of the IEEE 802.5 route descriptor
associated with this conceptual row."::={ lecRouteDescrEntry 1}lecRouteDescrBridgeNumber OBJECT-TYPESYNTAXINTEGER(0..15)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The Bridge Number portion of the IEEE 802.5 route
descriptor associated with this conceptual row."::={ lecRouteDescrEntry 2}lecRouteDescrAtmBinding OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The non-multiplexed ATM address, if any, registered
for the IEEE 802.5 route descriptor
('lecRouteDescrSegmentID',
'lecRouteDescrBridgeNumber')."::={ lecRouteDescrEntry 3}lecRouteDescrMuxedAtmBinding OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The LLC-multiplexed ATM address, if any, registered
for the IEEE 802.5 route descriptor
('lecRouteDescrSegmentID',
'lecRouteDescrBridgeNumber')."::={ lecRouteDescrEntry 4}lecRouteDescrServiceCategory OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"A bitmap describing the service categories which the
LEC supports for this route descriptor.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ lecRouteDescrEntry 5}-- ------------------------------------------------------------------- LAN Emulation Client ARP cache group - MAC addresses--leArpTable OBJECT-TYPESYNTAXSEQUENCEOF LeArpEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table provides access to an ATM LAN Emulation
Client's MAC-to-ATM ARP cache. It contains entries
for unicast addresses and for the broadcast address.
For LANE V2.0 clients whose C32 Selective Multicast
flag is set, this table will also contain multicast
address entries.
C16 LE_ARP Cache. A table of entries, each of which
establishes a relationship between a LAN
Destination external to the LE Client and the
ATM address to which data frames for that LAN
Destination will be sent."REFERENCE"ATM Forum LAN Emulation Over ATM Specification,
Section 5.1.1"::={ leClientMIBObjects 9}leArpEntry OBJECT-TYPESYNTAX LeArpEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An ATM LAN Emulation ARP cache entry containing
information about the binding of one MAC address
to one ATM address."INDEX{ lecIndex, leArpMacAddress }::={ leArpTable 1}
LeArpEntry ::=SEQUENCE{
leArpMacAddress MacAddress,
leArpAtmAddress AtmLaneAddress,
leArpIsRemoteAddress TruthValue,
leArpEntryType LeArpTableEntryType,
leArpRowStatus RowStatus,---- New for LANE 2.0--
leArpMuxedAtmAddress AtmLaneAddress,
leArpServiceCategory INTEGER}leArpMacAddress OBJECT-TYPESYNTAXMacAddressMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The MAC address for which this cache entry provides
a translation. Since ATM LAN Emulation uses an ARP
protocol to locate the Broadcast and Unknown Server,
the value of this object could be the broadcast MAC
address. Starting with LANE Version 2.0, the value
could also be a multicast or group MAC address.
Unicast MAC addresses should be unique within any
given ATM Emulated LAN. However, there's no
requirement that they be unique across disjoint
emulated LANs."::={ leArpEntry 1}leArpAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The non-multiplexed LE Client or Broadcast/Multicast
Service ATM address corresponding to the MAC address
'leArpMacAddress'.
This value may be determined through the use of the
LE_ARP procedure, through source address learning,
or through other mechanisms.
Some agents may provide write access to this object,
as part of their support for 'static' LE_ARP entries.
The effect of attempting to write an ATM address to
a 'learned' row is explicitly undefined. Agents may
disallow the write, accept the write and change the
row's type, or even accept the write as-is."::={ leArpEntry 2}leArpIsRemoteAddress OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates whether this entry is for a local or remote
MAC address.
In this context, 'local' means 'a MAC address that is
local to the remote client', as opposed to 'one of my
addresses'.
true(1)
The address is believed to be remote - or its
local/remote status is unknown.
For an entry created via the LE_ARP mechanism,
this corresponds to the 'Remote address' flag
being set in the LE_ARP_RESPONSE.
During Topology Change periods, remote LE_ARP
entries generally age out faster than others.
Specifically, they are subject to the Forward
Delay Time as well as to the Aging Time.
false(2)
The address is believed to be local - that is
to say, registered with the LES by the client
whose ATM address is leArpAtmAddress (and/or
leArpMuxedAtmAddress).
For an entry created via the LE_ARP mechanism,
this corresponds to the 'Remote address' flag
being cleared in the LE_ARP_RESPONSE."::={ leArpEntry 3}leArpEntryType OBJECT-TYPESYNTAXLeArpTableEntryTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates how this LE_ARP table entry was created and
whether it is aged."DEFVAL{ staticVolatile }::={ leArpEntry 4}leArpRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Lets users create and delete LE_ARP cache entries,
on systems that support this capability.
Normally clients will maintain their LE_ARP caches
automatically. However, managers may occasionally
want to create 'static' LE_ARP cache entries.
Rules
1. Before a new row can become 'active', values
must be supplied for the columnar objects
leArpAtmAddress and leArpEntryType.
The value for leArpAtmAddress may be a zero-
length address if there is an ATM address in
the leArpMuxedAtmAddress, and the LE_ARP row
belongs to a LEC running LANE 2.0 or higher.
2. It is not necessary to set leArpRowStatus to
'notInService' in order to modify a writable
object in the same conceptual row.
3. LE_ARP entries whose status is 'notReady' or
'notInService' will not be used to translate
LAN Destinations to ATM Addresses. However,
clients may overwrite such entries with data
obtained from other sources. For example, a
client which needed to transmit a data frame
to a given MAC address (or via a given Route
Descriptor) might find that its LE_ARP entry
for the LAN Destination is 'notInService' or
'notReady'. The client might then act as if
the LAN Destination was unknown - generating
a LE_ARP_REQUEST, flooding the data frame to
the BUS, and creating a new, 'active' LE_ARP
cache entry based on the LE_ARP_RESPONSE."::={ leArpEntry 5}leArpMuxedAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The LLC-multiplexed LE Client or Broadcast/Multicast
Service ATM address corresponding to the MAC address
'leArpMacAddress'.
This value may be determined through the use of the
LE_ARP procedure, through source address learning,
or through other mechanisms.
Some agents may provide write access to this object,
as part of their support for 'static' LE_ARP entries.
The effect of attempting to write an ATM address to
a 'learned' row is explicitly undefined. Agents may
disallow the write, accept the write and change the
row's type, or even accept the write as-is."::={ leArpEntry 6}leArpServiceCategory OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"A bitmap describing the service categories which the
LEC 'lecIndex' supports.
This value normally comes from the optional 'Service-
Category' TLV in LANE 2.0 LE_ARP_RESPONSEs.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion.
If service categories aren't applicable, aren't known,
or the implementor does not want to provide memory to
store them (e.g., because they would only be used for
SNMP), this object should be set to the value 0.
See also the object 'lecStoresServiceCategories'."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"
::={ leArpEntry 7}-- ------------------------------------------------------------------- LAN Emulation Client ARP cache group - Route Descriptors--leRDArpTable OBJECT-TYPESYNTAXSEQUENCEOF LeRDArpEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table provides access to an ATM LAN Emulation
Client's Route Descriptor-to-ATM ARP cache.
Implementation of this table is optional for hosts
that do not support emulated IEEE 802.5 Token Ring
LANs, and mandatory for hosts which do.
C16 LE_ARP Cache. A table of entries, each of which
establishes a relationship between a LAN
Destination external to the LE Client and the
ATM address to which data frames for that LAN
Destination will be sent."REFERENCE"ATM Forum LAN Emulation Over ATM Specification,
Section 5.1.1"::={ leClientMIBObjects 10}leRDArpEntry OBJECT-TYPESYNTAX LeRDArpEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An ATM LAN Emulation ARP cache entry containing
information about the binding of one IEEE 802.5
route descriptor to one ATM address."INDEX{ lecIndex, leRDArpSegmentID, leRDArpBridgeNumber }::={ leRDArpTable 1}
LeRDArpEntry ::=SEQUENCE{
leRDArpSegmentID INTEGER,
leRDArpBridgeNumber INTEGER,
leRDArpAtmAddress AtmLaneAddress,
leRDArpEntryType LeArpTableEntryType,
leRDArpRowStatus RowStatus,---- New for LANE 2.0--
leRDArpMuxedAtmAddress AtmLaneAddress,
leRDArpServiceCategory INTEGER,
leRDArpIsRemoteDescriptor TruthValue
}leRDArpSegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The LAN ID portion of the IEEE 802.5 route descriptor
associated with this ARP cache entry."::={ leRDArpEntry 1}leRDArpBridgeNumber OBJECT-TYPESYNTAXINTEGER(0..15)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The Bridge Number portion of the IEEE 802.5 route
descriptor associated with this ARP cache entry."::={ leRDArpEntry 2}leRDArpAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The non-multiplexed ATM address of the LAN Emulation
Client which is associated with the route descriptor
('leRDArpSegmentID', 'leRDArpBridgeNumber').
This value may be determined through the use of the
LE_ARP procedure, through source address learning,
or through other mechanisms.
Some agents may provide write access to this object,
as part of their support for 'static' LE_ARP entries.
The effect of attempting to write an ATM address to
a 'learned' row is explicitly undefined. Agents may
disallow the write, accept the write and change the
row's type, or even accept the write as-is."::={ leRDArpEntry 3}leRDArpEntryType OBJECT-TYPESYNTAXLeArpTableEntryTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates how this LE_ARP table entry was created and
whether it is aged."DEFVAL{ staticVolatile }::={ leRDArpEntry 4}
leRDArpRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Lets users create and delete LE_ARP cache entries,
on systems that support this capability.
Normally clients will maintain their LE_ARP caches
automatically. However, managers may occasionally
want to create 'static' LE_ARP cache entries.
Rules
1. Before a new row can become 'active', values
must be supplied for the columnar objects
leRDArpAtmAddress and leRDArpEntryType.
2. It is not necessary to set leRDArpRowStatus to
'notInService' in order to modify a writable
object in the same conceptual row.
3. LE_ARP entries whose status is 'notReady' or
'notInService' will not be used to translate
LAN Destinations to ATM Addresses. However,
clients may overwrite such entries with data
obtained from other sources. For example, a
client which needed to transmit a data frame
to a given MAC address (or via a given Route
Descriptor) might find that its LE_ARP entry
for the LAN Destination is 'notInService' or
'notReady'. The client might then act as if
the LAN Destination was unknown - generating
a LE_ARP_REQUEST, flooding the data frame to
the BUS, and creating a new, 'active' LE_ARP
cache entry based on the LE_ARP_RESPONSE."::={ leRDArpEntry 5}leRDArpMuxedAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The LLC-multiplexed ATM address of the LAN Emulation
Client which is associated with the route descriptor
('leRDArpSegmentID', 'leRDArpBridgeNumber').
This value may be determined through the use of the
LE_ARP procedure, through source address learning,
or through other mechanisms.
Some agents may provide write access to this object,
as part of their support for 'static' LE_ARP entries.
The effect of attempting to write an ATM address to
a 'learned' row is explicitly undefined. Agents may
disallow the write, accept the write and change the
row's type, or even accept the write as-is."::={ leRDArpEntry 6}leRDArpServiceCategory OBJECT-TYPE
SYNTAXINTEGER(0..2147483647)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"A bitmap describing the service categories which the
LEC 'lecIndex'supports.
This value normally comes from the optional 'Service-
Category' TLV in LANE 2.0 LE_ARP_RESPONSEs.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion.
If service categories aren't applicable, aren't known,
or the implementor does not want to provide memory to
store them (e.g., because they would only be used for
SNMP), this object should be set to the value 0.
See also the object 'lecStoresServiceCategories'."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ leRDArpEntry 7}leRDArpIsRemoteDescriptor OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates whether this entry is for a local or remote
route descriptor.
In this context, 'local' means 'a route descriptor
that is local to the remote client', as opposed to
'one of my route descriptors'.
true(1)
The route descriptor is believed to be remote
- or its local/remote status is unknown.
For an entry created via the LE_ARP mechanism,
this corresponds to the 'Remote address' flag
being set in the LE_ARP_RESPONSE.
false(2)
The route descriptor is believed to be local
- that is to say, registered with the LES by
the client whose address is leRDArpAtmAddress
(and/or leRDArpMuxedATMAddress).
For an entry created via the LE_ARP mechanism,
this corresponds to the 'Remote address' flag
being cleared in the LE_ARP_RESPONSE."::={ leRDArpEntry 8}-- ------------------------------------------------------------------- LAN Emulation Client - Multicast Forward VCC table--lecMcForwardTable OBJECT-TYPESYNTAXSEQUENCEOF LecMcForwardEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table identifying Multicast Forward VCCs for LAN
Emulation Version 2.0 clients."::={ leClientMIBObjects 11}lecMcForwardEntry OBJECT-TYPESYNTAX LecMcForwardEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each row represents one Multicast Forward VCC."INDEX{ lecIndex,
lecMcForwardInterface,
lecMcForwardVpi,
lecMcForwardVci }::={ lecMcForwardTable 1}
LecMcForwardEntry ::=SEQUENCE{
lecMcForwardInterface LeConnectionInterface,
lecMcForwardVpi VpiInteger,
lecMcForwardVci VciInteger,
lecMcForwardVerification INTEGER}lecMcForwardInterface OBJECT-TYPESYNTAXLeConnectionInterfaceMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The interface associated with the Multicast Forward
VCC."::={ lecMcForwardEntry 1}lecMcForwardVpi OBJECT-TYPESYNTAXVpiIntegerMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The VPI which identifies the Multicast Forward VCC
at the point where it connects to the LANE client."::={ lecMcForwardEntry 2}lecMcForwardVci OBJECT-TYPESYNTAXVciIntegerMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The VCI which identifies the Multicast Forward VCC
at the point where it connects to the LANE client."::={ lecMcForwardEntry 3}lecMcForwardVerification OBJECT-TYPESYNTAXINTEGER{none(1),implicit(2),explicit(3)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates whether the calling address for this VCC
has been verified.
none - No verification
implicit - Calling party address was same as
BUS address
explicit - Client used LE_VERIFY protocol
Also serves double-duty as a 'row exists' flag."::={ lecMcForwardEntry 4}-- ------------------------------------------------------------------- LAN Emulation Client - LE_ARP Response Group------ These optional objects let a network manager find out the ATM-- addresses associated with a proxy client's "C27 Remote Unicast-- MAC Address(es)" and "C30 Remote Route Descriptor(s)".---- They can also be used to find out the ATM addresses associated-- with a client's "C6 Local Unicast MAC Address(es)" and "C8-- Local Route Descriptor(s)".------ In the interests of efficiency and of not creating a big table-- that's the size of a bridge's forwarding database, the objects-- operate on a request-response model:---- 1. The network management system does a SET operation-- indicating the specific MAC address or segment ID/-- bridge number, and the specific client.---- 2. If the agent's MIB handler accepts the SET request,-- it triggers a query and updates the lecMacQuery* or-- lecRdQuery* objects.---- 3. The network management system does a GET operation-- to read the results. Ideally it should GET all of-- the result objects in one operation and check that
-- the result keys are the same as the query keys, to-- handle the case of simultaneous use by another NMS.--lecQueryObjects OBJECTIDENTIFIER::={ leClientMIBObjects 12}---- MAC address queries--lecMacQueryObjects OBJECTIDENTIFIER::={ lecQueryObjects 1}lecMacQueryLecIndex OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 'lecIndex' of the LEC whose MAC address binding
the network management station wants to look up.
When written: Triggers a new query.
When read: Identifies the last LEC queried. (This
value may be 0 if there have been no queries, or if
a LEC has been deleted.)"::={ lecMacQueryObjects 1}lecMacQueryAddress OBJECT-TYPESYNTAXMacAddressMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The MAC address whose binding the network management
station wants to look up.
When written: Triggers a new query. (Note that the
SNMP agent is free to reject multicast and broadcast
addresses with a 'badValue' error.)
When read: Returns the last MAC address queried, or
all zeroes if lecMacQueryLecIndex is 0."::={ lecMacQueryObjects 2}lecMacQueryStatus OBJECT-TYPESYNTAXINTEGER{none(1),unsupported(2),local(3),remote(4),unknown(5)}
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The status of the last query - one of the following:
none(1)
No queries have been made; therefore, other
results values are invalid.
unsupported(2)
Queries are not supported for this LEC.
local(3)
The MAC address is one of the client's local
MAC addresses.
remote(4)
The MAC address is one of the client's remote
MAC addresses.
unknown(5)
The MAC address does not belong (is not known
to belong) to the client."::={ lecMacQueryObjects 3}lecMacQueryAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The non-multiplexed ATM address which this client --
i.e., client 'lecMacQueryLecIndex' -- would use in a
LE_ARP_RESPONSE for 'lecMacQueryAddress'.
This object is only meaningful when lecMacQueryStatus
is 'localMacAddress' or 'remoteMacAddress'."::={ lecMacQueryObjects 4}lecMacQueryMuxedAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The LLC-multiplexed ATM address which this client --
i.e., client 'lecMacQueryLecIndex' -- would use in a
LE_ARP_RESPONSE for 'lecMacQueryAddress'.
This object is only meaningful when lecMacQueryStatus
is 'localMacAddress' or 'remoteMacAddress'."::={ lecMacQueryObjects 5}lecMacQueryServiceCategory OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Service Category TLV that this client would use
in a LE_ARP_RESPONSE for 'lecMacQueryAddress'.
If this client wouldn't return a Service Category TLV
in the LE_ARP_RESPONSE, this object should be set to
zero.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion.
This object is only meaningful when lecMacQueryStatus
is 'localMacAddress' or 'remoteMacAddress'."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ lecMacQueryObjects 6}---- Route Descriptor queries--lecRDQueryObjects OBJECTIDENTIFIER::={ lecQueryObjects 2}lecRDQueryLecIndex OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 'lecIndex' of the LEC whose route descriptor to
ATM address binding the network management station
wants to look up.
When written: Triggers a new query.
When read: Identifies the last LEC queried. (This
value may be 0 if there have been no queries, or if
a LEC has been deleted.)"::={ lecRDQueryObjects 1}lecRDQuerySegmentID OBJECT-TYPESYNTAXINTEGER(0..4095)MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The LAN ID portion of the IEEE 802.5 route descriptor
whose binding the network management station wants to
look up.
When written: Triggers a new query.
When read: Returns the LAN ID portion of the last RD
queried, or 0 if lecRDQueryLecIndex is 0."::={ lecRDQueryObjects 2}lecRDQueryBridgeNumber OBJECT-TYPESYNTAXINTEGER(0..15)MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The bridge number portion of the IEEE 802.5 route
descriptor whose binding the network management
station wants to look up.
When written: Triggers a new query.
When read: Returns the bridge number portion of the
last RD queried, or 0 if lecRDQueryLecIndex is 0."::={ lecRDQueryObjects 3}lecRDQueryStatus OBJECT-TYPESYNTAXINTEGER{none(1),unsupported(2),local(3),remote(4),unknown(5)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The status of the last query - one of the following:
none(1)
No queries have been made; therefore, other
results values are invalid.
unsupported(2)
Queries are not supported for this LEC.
local(3)
The route descriptor is one of the client's
local route descriptors.
remote(4)
The route descriptor is one of the client's
remote route descriptors.
unknown(5)
The route descriptor does not belong (is not
known to belong) to the client."::={ lecRDQueryObjects 4}lecRDQueryAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The non-multiplexed ATM address which this client --
i.e., client 'lecRDQueryLecIndex' -- would use in a
LE_ARP_RESPONSE for the route descriptor
('lecRDQuerySegmentID', 'lecRDQueryBridgeNumber').
This object is only meaningful when lecRDQueryStatus
is 'local' or 'remote'."::={ lecRDQueryObjects 5}lecRDQueryMuxedAtmAddress OBJECT-TYPESYNTAXAtmLaneAddressMAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The LLC-multiplexed ATM address which this client --
i.e., client 'lecRDQueryLecIndex' -- would use in a
LE_ARP_RESPONSE for the route descriptor
('lecRDQuerySegmentID', 'lecRDQueryBridgeNumber').
This object is only meaningful when lecRDQueryStatus
is 'local' or 'remote'."::={ lecRDQueryObjects 6}lecRDQueryServiceCategory OBJECT-TYPESYNTAXINTEGER(0..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Service Category TLV that this client would use
in a LE_ARP_RESPONSE for the route descriptor
('lecRDQuerySegmentID', 'lecRDQueryBridgeNumber').
If this client wouldn't return a Service Category TLV
in the LE_ARP_RESPONSE, this object should be set to
zero.
The bitmap is larger than the LANE 2.0 specification
requires, in case room is ever needed for expansion.
This object is only meaningful when lecRDQueryStatus
is 'local' or 'remote'."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ lecRDQueryObjects 7}-- ------------------------------------------------------------------- LAN Emulation Client TLVs--lecTlvTable OBJECT-TYPESYNTAXSEQUENCEOF LecTlvEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table provides a place for an agent to store
interesting TLVs associated with
o Registered LAN destinations
o LE_ARP entries
o Query results from the LE_ARP response group
o Initialization / configuration
and any other categories the ATM Forum adds.
Unless otherwise stated,
o Entries in this table are completely optional.
o An implementation may choose to keep only the
TLVs which are 'interesting' to its designers,
such as MPOA TLVs in LE_ARP_RESPONSEs.
o TLVs which already have their own MIB objects
should not be duplicated here.
o Where write / create access is allowed, it is
not mandatory.
Implementors should document the specific lecTlvTable
features of their agent."REFERENCE"LAN Emulation Over ATM Version 2 - LUNI Specification,
Annex A (LAN Emulation Control Frame TLVs)"::={ leClientMIBObjects 13}lecTlvEntry OBJECT-TYPESYNTAX LecTlvEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each table row describes one TLV of a related set."INDEX{ lecIndex, lecTlvSetIndex, lecTlvLanDestination,
lecTlvIndex }::={ lecTlvTable 1}
LecTlvEntry ::=SEQUENCE{
lecTlvSetIndex INTEGER,
lecTlvLanDestination OCTETSTRING,
lecTlvIndex INTEGER,
lecTlvType OCTETSTRING,
lecTlvValue OCTETSTRING,
lecTlvRowStatus RowStatus}lecTlvSetIndex OBJECT-TYPESYNTAXINTEGER{layer3Tlvs(1),actualRegTlvs(2),configRegTlvs(3),leArpTlvs(4),queryTlvs(5)}MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An index which helps to identify a set of TLVs, and to
indicate their purpose.
The value of this index defines the interpretation and
use of corresponding table rows as follows:
layer3Tlvs(1)
-------------
This index provides access to Layer-3-Address
TLVs (Initial State variable C36) used during
the Initialization phase.
TLVs are stored in rows
( lecIndex, 1,
LAN_Destination( all '00's ),
* )
These rows may be read / created / written /
deleted.
actualRegTlvs(2)
----------------
This index provides access to TLVs which were
used to register LAN Destinations.
These TLVs are associated with entries in the
lecMacAddressTable and lecRouteDescrTable and
stored in rows
( lecIndex, 2,
LAN_Destination( lecMacAddress ),
* )
( lecIndex, 2,
LAN_Destination(
lecRouteDescrSegmentID,
lecRouteDescrBridgeNumber ),
* )
These rows may be read or deleted, but cannot
be created or modified. Most implementations
are expected to make them read-only.
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
configRegTlvs(3)
----------------
This index provides a way to set registration
TLVs for unregistered LAN Destinations.
Hopefully this is not something that managers
will need to do a lot.
TLVs are stored in rows
( lecIndex, 3,
LAN_Destination( the_LAN_destination ),
* )
Note that the agent might restrict the set of
LAN Destinations and TLVs that it allows; for
instance, to screen out the 'V2 Capable' TLV.
leArpTlvs(4)
------------
This index provides access to TLVs associated
with the LE_ARP cache.
These TLVs are associated with leArpTable and
leRDArpTable, and stored in rows
( lecIndex, 4,
LAN_Destination( leArpMacAddress ),
* )
( lecIndex, 4,
LAN_Destination(
leRDArpSegmentID,
leRDArpBridgeNumber ),
* )
Agents may allow write/create access to TLVs
when the type of the associated LE_ARP entry
is 'staticVolatile', 'staticNonVolatile', or
'other'.
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
queryTlvs(5)
------------
This index provides access to TLVs associated
with the last MAC Address or Route Descriptor
query.
TLVs are associated with lecMacQueryObjects &
lecRDQueryObjects, and stored in rows
( lecIndex, 5,
LAN_Destination( lecMacQueryAddress ),
* )
( lecIndex, 5,
LAN_Destination(
lecRDQuerySegmentID,
lecRDQueryBridgeNumber ),
* )
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
Additional indices may be defined by the ATM Forum as
needed."::={ lecTlvEntry 1}lecTlvLanDestination OBJECT-TYPESYNTAXOCTETSTRING(SIZE(8))MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The MAC address or route descriptor associated with
the TLV (see the description of the lecTlvSetIndex),
encoded in the fashion defined in the LANE 2.0 LUNI
specification (Table 16). To recap:
The first two octets indicate the LAN Destination's
type: 00, 01 for a MAC address; 00, 02 for a route
descriptor; 00, 00 for 'no LAN Destination'.
The next six octets contain either the MAC address,
or four 00 octets followed by the route descriptor,
or six nulls.
Note:
-----
In the future, the ATM Forum may extend this field
for use with other types of index values, provided
that each new type of index value has a unique tag.
Such extensions are NOT to be considered a 'change
in semantics' that requires the deprecation of the
index object and the table.
Network management system implementors are advised
to display values whose tags they do not recognize
as (formatted) hexadecimal strings."::={ lecTlvEntry 2}lecTlvIndex OBJECT-TYPESYNTAXINTEGER(1..65535)
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An arbitrary index which allows a set to contain
multiple TLVs."::={ lecTlvEntry 3}lecTlvType OBJECT-TYPESYNTAXOCTETSTRING(SIZE(4))MAX-ACCESSread-createSTATUScurrentDESCRIPTION"A four-octet string indicating this item's type.
It consists of a three-octet OUI, followed by an
octet identifying one of the organization's TLVs."::={ lecTlvEntry 4}lecTlvValue OBJECT-TYPESYNTAXOCTETSTRING(SIZE(0..255))MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The value - and, implicitly, the length - of the
TLV."::={ lecTlvEntry 5}lecTlvRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Provides a way for network managers to create and
delete rows in the TLV table."::={ lecTlvEntry 6}-- Conformance InformationleClientMIBConformance OBJECTIDENTIFIER::={ leClientMIB 2}leClientMIBGroups OBJECTIDENTIFIER::={ leClientMIBConformance 1}leClientMIBCompliances OBJECTIDENTIFIER::={ leClientMIBConformance 2}
-- Compliance StatementsleClientMIBCompliance MODULE-COMPLIANCESTATUSdeprecatedDESCRIPTION"The original compliance statement for SNMP
entities which supported ATM LAN Emulation
Clients.
See leClientMIBCompliance2 for the updated
statement.
For a host to conform to this MIB, it must also implement
- RFC 1213 - MIB II.
- Interfaces table entries for each LE Client, as per the
LAN Emulation Client management specification.
- The AToM MIB (RFC 1695 - Definitions of Managed Objects
for ATM Management), according to the conformance
statements defined in that RFC.
Optionally, a host may implement
- RFC 1573 - Evolution of the Interfaces Group of MIB-II.
- The 'ifRcvAddressGroup' from RFC 1573, which provides a
way to represent and configure interfaces with multiple
addresses.
See the LAN Emulation Client management specification for
interpretations of RFC 1573 / MIB-II as they apply to LAN
Emulation Clients."MODULE-- this moduleMANDATORY-GROUPS{leClientConfigGroup,
leClientStatusGroup,
leClientMappingGroup,
leClientStatisticsGroup,
leClientServerVccGroup,
leClientAtmAddressesGroup,
leClientMacAddressesGroup,
leClientArpGroup}GROUP leClientRouteDescriptorsGroup
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."GROUP leClientRDArpGroup
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."---- Minimum access definitions for objects--OBJECT lecRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecOwner
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigMode
MIN-ACCESSread-only
DESCRIPTION"Write access is not required."OBJECT lecConfigLanType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required.
Implementations are not required to
support all legal values."OBJECT lecConfigMaxDataFrameSize
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required.
Implementations are not required to
support all legal values."OBJECT lecConfigLanName
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLesAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecControlTimeout
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxUnknownFrameCount
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxUnknownFrameTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecVccTimeoutPeriod
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxRetryCount
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecAgingTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecForwardDelayTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecExpectedArpResponseTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."
OBJECT lecFlushTimeOut
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecPathSwitchingDelay
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecLocalSegmentID
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendAvgRate
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendPeakRate
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConnectionCompleteTimer
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecAtmAddressStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpEntryType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpEntryType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."
OBJECT leRDArpRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ leClientMIBCompliances 1}leClientMIBCompliance2 MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities
that support LECs and Version 2 of the LEC
management specification.
For a host to conform to this MIB, it must also implement
- RFC 1213 - MIB II.
- Interfaces table entries for each LE Client, as per the
LAN Emulation Client management specification.
- The AToM MIB (RFC 1695 - Definitions of Managed Objects
for ATM Management), according to the conformance
statements defined in that RFC.
Optionally, a host may implement
- RFC 1573 - Evolution of the Interfaces Group of MIB-II.
- The 'ifRcvAddressGroup' from RFC 1573, which provides a
way to represent and configure interfaces with multiple
addresses.
See the LAN Emulation Client management specification for
interpretations of RFC 1573 / MIB-II as they apply to LAN
Emulation Clients."MODULE-- this moduleMANDATORY-GROUPS{leClientStatusGroup,
leClientMappingGroup,
leClientStatisticsGroup,
leClientServerVccGroup,
leClientAtmAddressesGroup,
leClientMacAddressesGroup,
leClientArpGroup,
leClientConfigGroupV1,
leClientConfigGroupV2,
leClientStatusGroupV2,
leClientStatisticsGroupV2,
leClientAtmAddressesGroupV2,
leClientMacAddressesGroupV2,
leClientArpGroupV2,
leClientMcForwardGroup}GROUP leClientRouteDescriptorsGroup
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."GROUP leClientRouteDescriptorsGroupV2
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."GROUP leClientRDArpGroup
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."GROUP leClientRDArpGroupV2
DESCRIPTION"This group is mandatory only for hosts
that support emulated 802.5 LANs."GROUP leClientMacQueryGroup
DESCRIPTION"This group is optional."GROUP leClientRDQueryGroup
DESCRIPTION"This group is optional."GROUP leClientTlvGroup
DESCRIPTION"This group is optional."---- Minimum access definitions for objects--OBJECT lecRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecOwner
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigMode
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLanType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required.
Implementations are not required to
support all legal values."OBJECT lecConfigMaxDataFrameSize
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required.
Implementations are not required to
support all legal values."OBJECT lecConfigLanName
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLesAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecControlTimeout
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."
OBJECT lecMaxUnknownFrameTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecVccTimeoutPeriod
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxRetryCount
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecAgingTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecForwardDelayTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecExpectedArpResponseTime
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecFlushTimeOut
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecPathSwitchingDelay
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendAvgRate
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMulticastSendPeakRate
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConnectionCompleteTimer
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLecsAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecInitialControlTimeout
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecControlTimeoutMultiplier
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecV2MaxUnknownFrameCount
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLocalSegmentID
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigV2Capable
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigSelectiveMulticast
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecForwardDisconnectTimeout
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecConfigLLCMultiplexCapable
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMinReconfigureDelay
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxReconfigureDelay
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecMaxBusConnectRetries
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecTokenRingExplorerExclude
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecAtmAddressStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."
OBJECT lecAtmAddressMuxed
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpEntryType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpMuxedAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leArpServiceCategory
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpEntryType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpMuxedAtmAddress
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT leRDArpServiceCategory
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecTlvType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecTlvValue
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lecTlvRowStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ leClientMIBCompliances 2}-- Units of ConformanceleClientConfigGroup OBJECT-GROUPOBJECTS{ lecRowStatus, lecOwner,
lecConfigMode,
lecConfigLanType,
lecConfigMaxDataFrameSize,
lecConfigLanName,
lecConfigLesAtmAddress,
lecControlTimeout,
lecMaxUnknownFrameCount,
lecMaxUnknownFrameTime,
lecVccTimeoutPeriod,
lecMaxRetryCount,
lecAgingTime,
lecForwardDelayTime,
lecExpectedArpResponseTime,
lecFlushTimeOut,
lecPathSwitchingDelay,
lecLocalSegmentID,
lecMulticastSendType,
lecMulticastSendAvgRate,
lecMulticastSendPeakRate,
lecConnectionCompleteTimer }STATUSdeprecatedDESCRIPTION"A collection of objects used for creating and
configuring LAN Emulation Clients.
This group is deprecated because some objects
in it have been replaced by newer ones."::={ leClientMIBGroups 1}leClientStatusGroup OBJECT-GROUPOBJECTS{ lecIfIndex,
lecPrimaryAtmAddress,
lecID,
lecInterfaceState,
lecLastFailureRespCode,
lecLastFailureState,
lecProtocol, lecVersion,
lecTopologyChange,
lecConfigServerAtmAddress,
lecConfigSource,
lecActualLanType,
lecActualMaxDataFrameSize,
lecActualLanName,
lecActualLesAtmAddress,
lecProxyClient }STATUScurrentDESCRIPTION"A collection of objects describing the status
and operational parameters of the managed LAN
Emulation Clients."::={ leClientMIBGroups 2}leClientMappingGroup OBJECT-GROUPOBJECTS{ lecMappingIndex }STATUScurrentDESCRIPTION"A collection of objects which map a LAN Emulation
Client's 'ifIndex' to its 'lecIndex'."::={ leClientMIBGroups 3}leClientStatisticsGroup OBJECT-GROUPOBJECTS{ lecArpRequestsOut, lecArpRequestsIn,
lecArpRepliesOut , lecArpRepliesIn,
lecControlFramesOut,
lecControlFramesIn,
lecSvcFailures }STATUScurrentDESCRIPTION"A collection of objects which act as an extension
to the lecConfigTable.
These objects provide statistics on LAN Emulation
control traffic and SVC establishment."::={ leClientMIBGroups 4}leClientServerVccGroup OBJECT-GROUPOBJECTS{ lecConfigDirectInterface,
lecConfigDirectVpi,
lecConfigDirectVci,
lecControlDirectInterface,
lecControlDirectVpi,
lecControlDirectVci,
lecControlDistributeInterface,
lecControlDistributeVpi,
lecControlDistributeVci,
lecMulticastSendInterface,
lecMulticastSendVpi,
lecMulticastSendVci,
lecMulticastForwardInterface,
lecMulticastForwardVpi,
lecMulticastForwardVci }STATUScurrentDESCRIPTION"A collection of objects which act as an extension
to the lecConfigTable.
These objects identify Configuration Direct,
Control, and Multicast VCCs for each client,
making it easier to locate their entries in the
AToM MIB."::={ leClientMIBGroups 5}leClientAtmAddressesGroup OBJECT-GROUPOBJECTS{ lecAtmAddressStatus }STATUScurrentDESCRIPTION"A collection of objects which describe all of the
ATM addresses belonging to each client."::={ leClientMIBGroups 6}leClientMacAddressesGroup OBJECT-GROUPOBJECTS{ lecMacAddressAtmBinding }STATUScurrentDESCRIPTION"A collection of objects which describe all of the
MAC addresses registered for each client."::={ leClientMIBGroups 7}leClientRouteDescriptorsGroup OBJECT-GROUPOBJECTS{ lecRouteDescrAtmBinding }STATUScurrentDESCRIPTION"A collection of objects which describe all of the
Route Descriptors registered for each client."::={ leClientMIBGroups 8}leClientArpGroup OBJECT-GROUPOBJECTS{ leArpAtmAddress,
leArpIsRemoteAddress,
leArpEntryType,
leArpRowStatus }STATUScurrentDESCRIPTION"A collection of objects which describe the MAC-
to-ATM address mappings that this LAN Emulation
Client has learned."::={ leClientMIBGroups 9}
leClientRDArpGroup OBJECT-GROUPOBJECTS{ leRDArpAtmAddress, leRDArpEntryType,
leRDArpRowStatus }STATUScurrentDESCRIPTION"A collection of objects which describe the IEEE
802.5 Route Descriptor-to-ATM address mappings
that this LAN Emulation Client has learned."::={ leClientMIBGroups 10}leClientConfigGroupV1 OBJECT-GROUPOBJECTS{ lecRowStatus, lecOwner,
lecConfigMode,
lecConfigLanType,
lecConfigMaxDataFrameSize,
lecConfigLanName,
lecConfigLesAtmAddress,
lecControlTimeout,
lecMaxUnknownFrameTime,
lecVccTimeoutPeriod,
lecMaxRetryCount,
lecAgingTime,
lecForwardDelayTime,
lecExpectedArpResponseTime,
lecFlushTimeOut,
lecPathSwitchingDelay,
lecMulticastSendType,
lecMulticastSendAvgRate,
lecMulticastSendPeakRate,
lecConnectionCompleteTimer,
lecConfigLecsAtmAddress,
lecV2MaxUnknownFrameCount,
lecConfigLocalSegmentID }STATUScurrentDESCRIPTION"A collection of objects used for creating and
configuring both V1 and V2 LE Clients.
It is the same as leClientConfigGroup, except
that the deprecated objects lecLocalSegmentID
and lecMaxUnknownFrameCount have been removed
and replaced by lecV2MaxUnknownFrameCount and
lecConfigLocalSegmentID.
Also, lecConfigLecsAtmAddress has been added."::={ leClientMIBGroups 11}leClientConfigGroupV2 OBJECT-GROUP
OBJECTS{ lecInitialControlTimeout,
lecControlTimeoutMultiplier,
lecConfigV2Capable,
lecConfigSelectiveMulticast,
lecForwardDisconnectTimeout,
lecConfigLLCMultiplexCapable,
lecMinReconfigureDelay,
lecMaxReconfigureDelay,
lecMaxBusConnectRetries,
lecTokenRingExplorerExclude }STATUScurrentDESCRIPTION"A collection of objects which extend the LEC
configuration table to deal with LANE V2.0."::={ leClientMIBGroups 12}leClientStatusGroupV2 OBJECT-GROUPOBJECTS{ lecActualLocalSegmentID,
lecActualV2Capable,
lecElanID,
lecActualSelectiveMulticast,
lecActualLLCMultiplexCapable,
lecPreferredLesAddress,
lecStoresServiceCategories }STATUScurrentDESCRIPTION"A collection of objects which extend the LEC
status table to deal with LANE V2.0."::={ leClientMIBGroups 13}leClientStatisticsGroupV2 OBJECT-GROUPOBJECTS{ lecFlowFailures,
lecEchoDiscards,
lecFilteredMulticasts }STATUScurrentDESCRIPTION"A collection of objects which provide statistics
on LLC-multiplexed flow establishment, and count
harmless discards separately from ifInDiscards."::={ leClientMIBGroups 14}leClientAtmAddressesGroupV2 OBJECT-GROUPOBJECTS{ lecAtmAddressMuxed }STATUScurrentDESCRIPTION"An object which extends the lecAtmAddressTable to
provide information about LANE V2.0 multiplexing."::={ leClientMIBGroups 15}leClientMacAddressesGroupV2 OBJECT-GROUPOBJECTS{ lecMacAddressMuxedAtmBinding,
lecMacAddressServiceCategory }STATUScurrentDESCRIPTION"Objects which extend the lecMacAddressTable to
provide information about LANE V2.0 multiplexing
and TLVs."::={ leClientMIBGroups 16}leClientRouteDescriptorsGroupV2 OBJECT-GROUPOBJECTS{ lecRouteDescrMuxedAtmBinding,
lecRouteDescrServiceCategory }STATUScurrentDESCRIPTION"An object which extends the lecRouteDescrTable to
provide information about LANE V2.0 multiplexing."::={ leClientMIBGroups 17}leClientArpGroupV2 OBJECT-GROUPOBJECTS{ leArpMuxedAtmAddress,
leArpServiceCategory }STATUScurrentDESCRIPTION"A collection of objects which provide additional
LE-ARP information for LANE Version 2.0."::={ leClientMIBGroups 18}leClientRDArpGroupV2 OBJECT-GROUPOBJECTS{ leRDArpMuxedAtmAddress,
leRDArpServiceCategory,
leRDArpIsRemoteDescriptor }STATUScurrentDESCRIPTION"A collection of objects which provide additional
LE-ARP information for LANE Version 2.0."::={ leClientMIBGroups 19}leClientMcForwardGroup OBJECT-GROUPOBJECTS{ lecMcForwardVerification }STATUScurrentDESCRIPTION
"A collection of objects that provide information
on Multicast Forward VCCs belonging to LANE V2.0
clients."::={ leClientMIBGroups 20}leClientMacQueryGroup OBJECT-GROUPOBJECTS{ lecMacQueryLecIndex,
lecMacQueryAddress,
lecMacQueryStatus,
lecMacQueryAtmAddress,
lecMacQueryMuxedAtmAddress,
lecMacQueryServiceCategory }STATUScurrentDESCRIPTION"A collection of objects that allow a network
manager to find out ATM bindings for a proxy
client's remote MAC address(es)."::={ leClientMIBGroups 21}leClientRDQueryGroup OBJECT-GROUPOBJECTS{ lecRDQueryLecIndex,
lecRDQuerySegmentID,
lecRDQueryBridgeNumber,
lecRDQueryStatus,
lecRDQueryAtmAddress,
lecRDQueryMuxedAtmAddress,
lecRDQueryServiceCategory }STATUScurrentDESCRIPTION"A collection of objects that allow a network
manager to find out ATM bindings for a proxy
client's remote route descriptor(s)."::={ leClientMIBGroups 22}leClientTlvGroup OBJECT-GROUPOBJECTS{ lecTlvType,
lecTlvValue,
lecTlvRowStatus }STATUScurrentDESCRIPTION"A collection of objects that allow a network
manager to see 'interesting' TLV information."::={ leClientMIBGroups 23}END